ref(core): Constrain SdkProcessingMetadata to known keys
#15577
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AbhiPrasad
requested review from
mydea and
chargome
and removed request for
a team
size-limit report 📦
|
chargome
approved these changes
Mar 5, 2025
|
I guess this is a breaking change - but really nobody should be using these APIs other than us. Maybe we just leave a todo note and come back to this for v10? |
|
Will come back to this in v10 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After working on #15570, I realized we should be more constrained about what we set on
SdkProcessingMetadata.This PR updates the
SdkProcessingMetadatatype to be more constrained, not allowing any key to be passed to it. This should make sure we are more critical of changes that could lead to increased memory pressure in the SDK (asSdkProcessingMetadatalives alongside the scope).